Connection re-configuration upon beam recovery response

ABSTRACT

Systems, methods, and apparatus for connection re-configuration upon beam recovery are disclosed. An example method performed by a network node includes determining that a successful beam recovery has occurred with a wireless device. The network node determines one or more transmission parameters associated with the successful beam recovery, where the one or more transmission parameters are for re-configuring the wireless device. The network node transmits the one or more transmission parameters to the wireless device.

RELATED APPLICATIONS

The present application claims the benefit of priority from U.S.Provisional Application No. 62/544,641 entitled “ConnectionRe-Configuration Upon Beam Recovery Response” filed Aug. 11, 2017, thedisclosure of which is hereby incorporated herein in its entirety byreference.

TECHNICAL AREA

The present disclosure relates, in general, to wireless communicationsystems such as cellular networks, and more particularly, to methods,user equipment, and network nodes for performing connectionre-configuration.

BACKGROUND

In the Long-Term Evolution (LTE) standard, until Release 13, thereference signals that a user equipment (UE) used for the Channel StateInformation (CSI), Cell-Specific Reference Signal (CRS), and ChannelState Information Reference Signal (CSI-RS) were not pre-coded. The UEwas able to measure the raw channel and calculated feedback includingthe preferred precoding matrix. As the number of transmitter (Tx)antennas have increased, however, the amount of feedback has alsoincreased.

In Release 10 (Rel-10), when support for 8Tx closed loop precoding wasintroduced, a double codebook approach was introduced where the UE firstselected a wideband coarse precoder and then selected per subband asecond codeword. Another possible approach was for the network tobeamform the reference signal and for the UE to calculate feedback ontop of the reference signal. This approach was adopted in Rel-13 and wasone option provided in the Full-Dimension Multiple-Input Multiple-Output(FD-MIMO) specification, as described in the following section.

Beamformed Reference Signals in LTE

The Rel-13 FD-MIMO specification in LTE supports an enhanced CSI-RSreporting called Class B for beamformed CSI-RS. In the FD-MIMOspecification, an LTE RRC_CONNECTED UE can be configured with K beams(where 8>K>1) where there can be 1, 2, 4, or 8 port number for eachbeam. For CSI feedback purposes, such as providing a Precoding MatrixIndicator (PMI), Rank Indicator (RI) and Channel Quality Indicator(CQI), there is a CSI-RS Resource Indicator per CSI-RS. As shown in FIG.1, the UE report Channel State Information Reference Signal Index (CRI)indicates the preferred beam, where the CRI is wideband, RI/CQI/PMI isbased on legacy codebook (i.e. Rel-12), and the CRI reporting period isan integer multiple of the RI. For Rel-14 Enhanced Full-DimensionMultiple-Input Multiple-Output (eFD-MIMO), aperiodic CSI-RS wasintroduced with two different sub-flavors. The CRS-RS resources areconfigured for the UE as in Rel-13 and the set of K CSI-RS resources isconfigured to work as aperiodic or semipersistent. The UE waits for MAC(Medium Access Control) Coverage Enhancement (CE) activation for N outof K CSI-RS resources. For aperiodic CSI-RS, before reporting the UEwaits for a Downlink Control Information (DCI) activation of the CSI-RSresource, in addition to the MAC CE. For semi-persistent CSI-RS, the UEconsiders the CSI-RS activated after receiving the MAC CE.

The MAC CE activation/deactivation command is specified in TS36.321where Section 5.19 describes:

-   -   The network may activate and deactivate the configured CSI-RS        resources of a serving cell by sending the        Activation/Deactivation of CSI-RS resources MAC control element        described in subclause 6.1.3.14. The configured CSI-RS resources        are initially deactivated upon configuration and after a        handover.    -   Section 6.1.3.14 in view of FIGS. 2A and 2B states:    -   The Activation/Deactivation of CSI-RS resources MAC control        element is identified by a MAC PDU subheader with LCID as        specified in table 6.2.1-1. It has variable size as the number        of configured CSI process (N) and is defined in FIG. 6.1.3.14-1.        Activation/Deactivation CSI-RS command is defined in FIG.        6.1.3.14-2 and activates or deactivates CSI-RS resources for a        CSI process. Activation/Deactivation of CSI-RS resources MAC        control element applies to the serving cell on which the UE        receives the Activation/Deactivation of CSI-RS resources MAC        control element.

The Activation/Deactivation of CSI-RS resources MAC control elements isdefined as follows:

R_(i): this field indicates the activation/deactivation status of theCSI-RS resources associated with CSI-RS-ConfigNZPId i for the CSI-RSprocess. The R_(i) field is set to “1” to indicate that CSI-RS resourceassociated with CSI-RS-ConfigNZPId i for the CSI-RS process shall beactivated. The R_(i) field is set to “0” to indicate that theCSI-RS-ConfigNZPId i shall be deactivated.

The MAC activation was introduced in LTE to configure more CSI-RSresources for a UE, as the MAC CE would selective activate up to the maxCSI-RS resources supported by the UE. Then, without the need tore-configure by RRC, the network could activate another set among theresources configured for the UE.

Beam Forming in NR

For New Radio (NR), reference signals may be beamformed. In NR, thesynchronization sequences (Primary Synchronization Signal(NR-PSS)/Secondary Synchronization Signal (NR-SSS)) and PhysicalBroadcast Channel (PBCH) which includes Demodulation Reference Signal(DMRS) constitutes an SS Block. An RRC_CONNECTED UE trying to access atarget cell assumes that the SS Block may be transmitted in the form ofrepetitive bursts of SS Block transmissions (denoted “SS Burst”),wherein such a burst consists of a number of SS Block transmissionsfollowing close after each other in time. Furthermore, a set of SSBursts may be grouped together (denoted “SS Burst Set”), where the SSBursts in the SS Burst Sets are assumed to have some relation to eachother. Both SS Bursts and SS Burst Sets have their respective givenperiodicity. In the single beam scenarios, the network could configuretime-repetition within one SS Burst in a wide beam. In multi-beamscenarios, at least some of these signals and physical channels (e.g.,SS Block) would be transmitted in multiple beams, which could be done indifferent manners depending on network implementation, as shown in FIG.1.

FIG. 3 illustrates three example configurations of an SS Burst set. Thetop example illustrates a time-repetition within one SS Burst in a widebeam. The middle example represents a beam-sweeping of a small number ofbeams using only one SS Burst in the SS Burst set. The bottom exampleillustrates a beam-sweeping of a larger number of beams using more thanone SS Burst in the SS Burst Set to form a complete sweep. Which ofthese three alternatives to implement is a network vendor choice. Thatchoice depends on the tradeoff between i) the overhead caused bytransmitting periodic and always on narrow beam sweepings vs. ii) thedelays and signaling needed to configure the UE to find a narrow beamfor Physical Downlink Shared Channel (PDSCH)/Physical Downlink ControlChannel (PDCCH). The implementation shown in the upper figureprioritizes i), while the implementation shown in the bottom figureprioritizes ii). The figure in the middle case is an intermediate case,where a sweeping of wide beams is used. In that case the number of beamsto cover the cell is reduced, but in some cases an additional refinementis needed for narrow gain beamforming of PDSCH.

It is likely that network vendors will provide cell coverage with a lownumber of beams for the IDLE mode coverage which will imply a fairly lownumber of SS Blocks per Burst Set. Hence, once the UE accesses a cell,either via state transition to CONNECTED or via handovers, further beammanagement procedures need to be configured and Downlink (DL) beams tobe used for the transmission of PDCCH/PDSCH may need to be furtherrefined. For that purpose, Radio Access Network 1 (RAN1) is defining inNR a CSI-RS framework, to certain extent similar to LTE, for the beammanagement and CSI acquisition procedures or Transmission Point (TRP)recognition in same cell ID scenarios. The same cell ID scenario isequivalent to one of the LTE Coordinated Multipoint (CoMP) scenarioswhere concept of (LTE) transmission point (TP) was introduced. A TP/TRPis basically a remote radio head (RRH) and all RRHs have same cell IDwithin one cell area. This means that they all send the same CRS (inLTE) or SSB (in NR) and therefore CSI-RS is the only means for the UEthe separate a TP/TR.

NR has also adopted the terminology of aperiodic and semi persistentCSI-RS as well as aperiodic and semi-persistent CSI reporting that mayhappen from periodic, semipersistent or aperiodic CSI-RS with certainlimitations.

Beam Failure Detection and Beam Recovery Procedure

In NR, in order to improve coverage and increase data rate, beamformingis widely used. With beamforming, network can transmit user specificdata via narrow beam which can improve SINR. One issue with beam-basedtransmission is that since beams can provide quite narrow coverage, itis possible that suddenly UE is out of the coverage of the beam. If thatoccurs, the network would not be able to efficiently schedule data tothat UE and/or the UE would not be monitoring the right beam (or beamlink pair) used by the network to transmit a control channel (likePDCCH) and the UE would not be able to detect scheduled information.That problem is typically called “beam failure.”

3GPP has acknowledged the importance of that problem and started todiscuss for 5G a procedure called beam recovery upon the detection of abeam failure for RRC_CONNECTED UEs. In beam recovery, an RRC_CONNECTEDUE would perform measurements associated to the quality of the servinglink and, if that quality goes below a given threshold, the UE wouldperform beam recovery. The procedure aims to solve the situation wherethe TX and/or RX beams of the gNodeB and the UE have become misaligned,but where there are additional beams that could be used to maintain theconnection between the gNodeB and the UE. The beam failure recoveryprocedure includes the following aspects:

-   -   Beam failure detection: The UE monitors a certain periodic        reference signal (RS) to estimate the quality of the serving        link. Once the quality of that link falls below a certain        threshold, the UE initiates beam recovery.    -   New candidate beam identification: Once beam failure has been        detected, the UE tries to identify a new beam that would provide        adequate quality. The UE then searches for a specific RS, which        is transmitted from the same node, but in difference candidate        beams. During this search procedure, the UE may also change its        RX beam.    -   Beam failure recovery request: Once a new candidate beam has        been found, the UE transmits an Uplink (UL) signal using certain        UL resources. The gNodeB is prepared to receive the UL signal in        these UL resources, and can determine which candidate beam the        UE selected based on the receive UL signal.    -   Beam failure recovery response: When the gNodeB has received the        beam failure recovery request, it sends a DL response to        indicate to the UE that it received the request, using the        knowledge of the new beam. UE monitors gNodeB (gNB) response for        beam failure recovery request. Once the UE has successfully        received the response, the beam recovery is complete.

As described above, the last part of the beam failure recovery procedureinvolves the UE monitoring for a beam failure recovery response aftertransmitting a request and the network transmission of thatconfirmation. Concerning the content of that response message or thedefined UE monitoring behavior of that message, RAN1 has only agreed onthe following:

-   -   (RAN1 NR AdHoc #1) Support transmission of DL signal for        allowing the UE to monitor the beams for identifying new        potential beams;        -   FFS: Transmission of a beam swept control channel is not            precluded;        -   This mechanism(s) should consider tradeoff between            performance and DL signaling overhead;    -   (RAN1 #88-bis) UE monitors gNB response for beam failure        recovery request;    -   (RAN1 #88-bis) UE monitors a control channel search space to        receive gNB response for beam failure recovery request;        -   FFS: the control channel search space can be same or            different from the current control channel search space            associated with serving BPLs        -   FFS: UE further reaction if gNB does not receive beam            failure recovery request transmission    -   (RAN1 #89) FFS Contention-based Physical Random Access Channel        (PRACH) resources as supplement to contention-free beam failure        recovery resources    -   (RAN1 #89) To receive gNB response for beam failure recovery        request, a UE monitors NR PDCCH with the assumption that the        corresponding PDCCH DM-RS is spatial QCL'ed with RS of the        UE-identified candidate beam(s)        -   FFS whether the candidate beam(s) is identified from a            pre-configured set or not        -   Detection of a gNB's response for beam failure recovery            request during a time window is supported        -   FFS the time window is configured or pre-determined        -   FFS the number of monitoring occasions within the time            window        -   FFS the size/location of the time window        -   If there is no response detected within the window, the UE            may perform re-tx of the request (FFS details)        -   If not detected after a certain number of transmission(s),            UE notifies higher layer entities            -   FFS the number of transmission(s) or possibly further in                combination with or solely determined by a timer

NR Beam Recovery Procedure Based on RACH

Beam recovery shares some similarities with a random access procedure inthe sense that the UE selects a beam that is associated to a cell and,the beam is also associated to certain time, frequency and sequenceresources. The sequence in that case, is the one sent to indicate the DLbeam the UE has selected, and possibly the UE (if a dedicated preamble).After sending the preamble the UE also expects a response, as in beamrecovery. Similarly, the UE can also perform the beam selection based onCSI-RS or SS and RACH can be configured to either of these. Hence,although beam recovery is not defined, it is beneficial to describe someaspects of the random access procedure in NR.

An SS Burst Set is either transmitted in wide beams to cover the wholecell or even in a single beam. In the case the SS Burst Set istransmitted in a single wide beam, the handover command contains a RACHconfiguration for the target cell. Once the UE receives the handovercommand it will access the target and a random access procedure will betriggered by the UE sending a random access preamble. If directionalreciprocity is assumed, the target cell can transmit the Random AccessResponse (RAR) either by sweeping in multiple directions covering thewhole cell until the UE detects and transmits the handover completemessage or transmitting the RAR with time repetition (and expects thehandover (HO) complete message).

In the case multiple beams are used to transmit the SS Burst Set, thehandover command may contain multiple RACH configurations for the targetcell, possibly associated with the SS Block beams or groups of SS Blockbeams from target cell. Once the UE receives the handover command itwill select a beam in the target cell, check how it maps to the receivedRACH configuration per beam and initiate a random access procedure bysending a random access preamble associated with a target cell beam or agroup of beams.

FIG. 4 illustrates an example possible mapping from a beam to a RACHconfiguration. In the illustrated example, each SS Block contains amapping between RACH configuration and the strongest DL beamtransmitting the SS Block. Here, each PRACH occasion/resource isassociated with two SS Block beams. Even without directionalreciprocity, network implementation enables the target cell to transmitthe RAR in the strongest DL beam covering the UE thanks to the mappingbetween RACH configuration (including the preamble) and the target cellDL beam.

SUMMARY

The examples described in the present disclosure provide connectionre-configuration techniques that offer reduced overhead and fasterre-configuration, resulting in more efficient beam recovery. Otheradvantages may be readily apparent to one having skill in the art.Certain embodiments may have none, some, or all of the recitedadvantages.

An example method at a network node for connection re-configuration uponbeam recover includes determining that a successful beam recovery hasoccurred with a wireless device. The method further includes determiningone or more transmission parameters associated with the successful beamrecovery, the one or more transmission parameters for re-configuring thewireless device. The method further includes transmitting the one ormore transmission parameters to the wireless device.

An example method at a wireless device for connection re-configurationupon beam recovery includes receiving one or more transmissionparameters from a network node, where the one or more transmissionparameters are associated with a successful beam recovery. The methodfurther includes implementing the one or more transmission parametersreceived from the network node.

An example network node includes processing circuitry configured todetermine that a successful beam recovery has occurred and determine oneor more transmission parameters associated with the successful beamrecovery, where the one or more transmission parameters forre-configuring a wireless device. The network node further includes aninterface operably coupled to the processing circuitry, where theinterface is configured to transmit the one or more transmissionparameters to the wireless device.

An example wireless device includes an interface configured to receiveone or more transmission parameters from a network node, where the oneor more transmission parameters are associated with a successful beamrecovery. The wireless device further includes processing circuitryoperably coupled to the interface, where the processing circuitry isconfigured to implement the one or more transmission parameters receivedfrom the network node.

In yet other examples, a system including the user equipment and/ornetwork node are provided that perform the above methods. Further, thepresent disclosure also provides a non-transitory computer-readablemedium comprising computer instructions stored thereon that, whenexecuted by a processing circuit, cause the processing circuit toperform the above methods.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and theirfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings.

FIG. 1 illustrates a wireless communication network including beamformedCSI-RS according to embodiments of the present disclosure.

FIG. 2A illustrates a MAC control element for activation/deactivation ofCSI-RS resources according to embodiments of the present disclosure.

FIG. 2B illustrates an octet that includes bit indicators correspondingto a set of CSI-RS according to embodiments of the present disclosure.

FIG. 3 illustrates three example configurations of an SS Burst setaccording to embodiments of the present disclosure.

FIG. 4 illustrates a mapping from a beam to a RACH configurationaccording to embodiments of the present disclosure.

FIG. 5 illustrates sets of CSI-RS resources associated with DL beamsaccording to embodiments of the present disclosure.

FIG. 6 illustrates a re-configuration of CSI-RS parameters for beammanagement according to embodiments of the present disclosure.

FIG. 7 illustrates a schematic diagram of a wireless communicationnetwork according to embodiments of the present disclosure.

FIG. 8 illustrates a schematic block diagram of an exemplary radionetwork controller or core network node according to embodiments of thepresent disclosure.

FIG. 9 illustrates a schematic block diagram of a wireless deviceaccording to embodiments of the present disclosure.

FIG. 10 illustrates a schematic block diagram of a network nodeaccording to embodiments of the present disclosure.

FIG. 11 illustrates a signal flow between a wireless device and anetwork node according to certain embodiments of the present disclosure.

DETAILED DESCRIPTION

There are a number of technical issues associated with conventional beamrecovery response techniques. For example, potential changes beingdiscussed relate to beam recovery from a physical layer perspective, andinclude techniques for allowing the network to determine the best DLbeam for continuing scheduling relating to the UE, such as scheduling oftransmitting control channels. The discussions, however, do not addressany re-configuration of parameters upon a successful beam recovery orprovide techniques for performing such re-configuration.

Embodiments of the present disclosure overcome technical issues relatingto connection re-configuration upon beam recovery response, among othertechnical issues. For example, embodiments of the present disclosuredescribe systems and methods related to a beam failure recovery responsemessage that can be used to perform parameter re-configuration. In someembodiments, this beam failure recovery response message is used alongwith previously received messages that contain complementary informationand/or determinations based on the associated UE behavior. Moreover, insome embodiments, the technique includes providing a configuration ofsets of CSI-RS configuration for beam management in a target cell, andthe target node selects one of these configurations based on the UEPRACH preamble.

Certain embodiments consist of a method where the network can configure(or re-configure) a UE with transmission parameters (or inform that someparameters should be kept) upon the detection of a successful beamrecovery. After beam recovery, network knows the new DL Tx beam itshould use to contact the UE, the one(s) that the UE should also monitor(for PDCCH monitoring, for example) so the network can also adjust oneor a set of transmission parameters that may be affected by the factthat the UE has recovered its beam(s) and re-configure the UEaccordingly.

In some embodiments, the re-configuration upon beam recovery that is afull and/or delta re-configuration message, which can either be a RadioResource Control (RRC) Connection Re-configuration or a MAC CE messagecontaining the new parameters to be used and/or previously configuredand activated parameters that can remain active.

In another embodiment, the UE first receives a list of candidatere-configurations which are indexed (e.g. by an integer value) and oneor a subset of these can be further activated by the re-configurationupon beam recovery. For example, the subset could include an index to apreviously received configuration, which can be activated after beamrecovery to take into account a change of a beam.

In some embodiments, there are different types of re-configurationsincluding re-configurations relating to RLM, beam failure detection,beam recovery request transmission, monitoring of beam recoveryresponse, measurement configuration(s), cell quality derivationparameters, other parameters such as DMRS and/or any other scramblingcode(s), among others.

Different schemes may be used for certain embodiments such as: RRCmessages for the full and/or delta re-configuration or for the list ofre-configurations and indexes; and MAC CE messages for the activation ofpreviously provided configurations. In some embodiments, in a recoveryresponse message a MAC CE message can be given for the activation ofpreviously provided configurations.

Certain embodiments of the present disclosure may provide additionaltechnical advantages, such as that the UE can be re-configured to use anew set of parameters upon beam recovery where these parameters can berelated to the new DL beam being used by the network to contact the UE.An advantage of certain embodiments may include an optimization to speedup that re-configuration and/or reduce the overhead caused by RRCsignaling by allowing the network to use a MAC CE to activate aparticular configuration selected based on the new best beam the UE hasselected and indicated via beam recovery request. Accordingly, inaddition to providing new functionality for UE re-configuration thatpreviously did not exist, these techniques provide advantages of reducedoverhead and faster re-configuration, resulting in more efficient beamrecovery. Certain embodiments may have none, some, or all of the recitedadvantages, and other technical advantages may be readily apparent toone having skill in the art.

The technology described herein can be used in various wireless systemsand is not restricted to 3GPP EUTRA/LTE systems and 3GPP Next Generationsystems (also referred to as the 5G system or 5GS) deploying New Radio(NR), even though such systems will serve as examples. Moreover,different types of re-configurations could be performed due to thechange of a DL Tx and/or Rx beam(s), which could either be singlebeam(s) and/or beam link pair(s) (BPL)(s). Example re-configurationsinclude Radio Link Monitoring (RLM) related configuration (e.g. eitherthe RS type or, in the case of CSI-RS, the resource(s) to be monitored,the periodicities, beams, etc.), measurement configuration (for example,in the case of CSI-RS based measurements, to take into accountactivation of new resources and/or requests for monitoring by the UE),changes to scrambling codes (e.g. UE-specific DMRS), beam failuredetection configuration, and beam recovery configuration, among others.

FIG. 5 illustrates example set(s) of CSI-RS associated with DL beams. Inthe illustrated embodiment, the UE is connected to that cell whosestrongest beam detected by the UE was associated to SS Block-A. Hence,beam management is performed based on beam measurements and reports of aset of CSI-RS resources associated to DL beams in set-1, as shown inFIG. 5.

FIG. 6 illustrates re-configuration of CSI-RS parameters for beammanagement. As shown in FIG. 6, if the UE detects beam failure andperforms beam selection it determines that SS Block-B is the strongestand, upon selecting these and successfully performing beam recovery, theUE determines to not measure and report beams using set-1, but insteadmeasure and report beams using set-2. The change of set-1 to set-2 is are-configuration of CSI-RS parameters for beam management, and in someembodiments is similar to techniques for re-configuration correspondingto CSI acquisition, link adaptation, among others. Accordingly, asillustrated in the example embodiment of FIG. 6, the UE selects the SSBlock-B as its best DL beam and sends the RACH preamble associated tothis best DL beam and the target gNodeB identifies that UE is under thecoverage of SS Block-B. In some examples, a best beam is determined byidentifying a beam with a highest Signal-to-Noise (SNR) ratio or havinganother objective indicia of high signal quality.

FIG. 7 is a schematic diagram of a wireless communication network 700,in accordance with certain embodiments. In the illustrated embodiment,FIG. 7 includes network 720, network nodes 700 a-b, and wireless device710. Wireless device 710 may be interchangeably referred to as userequipment (UE) 710. In different embodiments, the wireless network maycomprise any number of wired or wireless networks, network nodes, basestations (BS), controllers, wireless devices, relay stations, and/or anyother components that may facilitate or participate in the communicationof data and/or signals whether via wired or wireless connections.

Network 720 may comprise one or more IP networks, public switchedtelephone networks (PSTNs), packet data networks, optical networks, widearea networks (WANs), local area networks (LANs), wireless local areanetworks (WLANs), wired networks, wireless networks, metropolitan areanetworks, and other networks to enable communication between devices.Network node 700 a may refer to any kind of network node 700, which maycomprise a Node B, base station (BS), radio base station, multi-standardradio (MSR) radio node such as MSR BS, eNode B, network controller,radio network controller (RNC), multi-cell/multicast coordination entity(MCE), base station controller (BSC), relay node, base transceiverstation (BTS), access point (AP), radio access point, transmissionpoints, transmission nodes, remote radio unit (RRU), remote radio head(RRH), nodes in distributed antenna system (DAS), core network node(e.g., MSC, MME, SON node, coordinating node, etc.), O&M, OSS,positioning node (e.g., E-SMLC), MDT, an external node (e.g.,third-party node, a node external to the current network), or anysuitable network node.

Network node 700 a comprises interface 701, processor 702, storage 703,and antenna 704. These components are depicted as single boxes locatedwithin a single larger box. In practice however, a network node 700 amay comprise multiple different physical components that make up asingle illustrated component (e.g., interface 701 may comprise terminalsfor coupling wires for a wired connection and a radio transceiver for awireless connection). As another example, network node 700 a may be avirtual network node in which multiple different physically separatecomponents interact to provide the functionality of network node 700 a(e.g., processor 702 may comprise three separate processors located inthree separate enclosures, where each processor is responsible for adifferent function for a particular instance of network node 700).Similarly, network node 700 a may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, a BTScomponent and a BSC component, etc.), which may each have their ownrespective processor, storage, and interface components. In certainscenarios in which network node 700 a comprises multiple separatecomponents (e.g., BTS and BSC components), one or more of the separatecomponents may be shared among several network nodes. For example, asingle RNC may control multiple NodeB's. In such a scenario, each uniqueNodeB and BSC pair, may be a separate network node. In some embodiments,network node 700 a may be configured to support multiple radio accesstechnologies (RATs). In such embodiments, some components may beduplicated (e.g., separate storage 703 for the different RATs) and somecomponents may be reused (e.g., the same antenna 704 may be shared bythe RATs).

Processor 702 may be a combination of one or more of a microprocessor,controller, microcontroller, central processing unit, digital signalprocessor, application specific integrated circuit, field programmablegate array, processing circuitry, or any other suitable computingdevice, resource, or combination of hardware, software and/or encodedlogic operable to provide, either alone or in conjunction with othernetwork node 700 a components, such as storage 703, network node 700 afunctionality. For example, processor 702 may execute instructionsstored in storage 703. Such functionality may include providing variouswireless features discussed herein to a wireless device, such aswireless device 710, including any of the features or benefits disclosedherein.

Storage 703 may comprise any form of volatile or non-volatile computerreadable memory including, without limitation, persistent storage, solidstate memory, remotely mounted memory, magnetic media, optical media,random access memory (RAM), read-only memory (ROM), removable media, orany other suitable local or remote memory component. Storage 703 maystore any suitable instructions, data or information, including softwareand encoded logic, utilized by network node 700. Storage 703 may be usedto store any calculations made by processor 702 and/or any data receivedvia interface 701.

Network node 700 a also comprises interface 701, which may be used inthe wired or wireless communication of signalling and/or data betweennetwork node 700, network 720, and/or wireless device 710. For example,interface 701 may perform any formatting, coding, or translating thatmay be needed to allow network node 700 a to send and receive data fromnetwork 720 over a wired connection. Interface 701 may also include aradio transmitter and/or receiver that may be coupled to or a part ofantenna 704. The radio may receive digital data that is to be sent outto other network nodes or wireless devices 710 via a wirelessconnection. The radio may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters. The radiosignal may then be transmitted via antenna 704 to the appropriaterecipient (e.g., wireless device 710).

Antenna 704 may be any type of antenna capable of transmitting andreceiving data and/or signals wirelessly. In some embodiments, antenna704 may comprise one or more omni-directional, sector or panel antennasoperable to transmit/receive radio signals between, for example, 2 GHzand 66 GHz. An omni-directional antenna may be used to transmit/receiveradio signals in any direction, a sector antenna may be used totransmit/receive radio signals from devices within a particular area,and a panel antenna may be a line of sight antenna used totransmit/receive radio signals in a relatively straight line.

Wireless device 710 may be any type of wireless endpoint, mobilestation, mobile phone, wireless local loop phone, smartphone, userequipment (UE), desktop computer, PDA, cell phone, tablet, laptop, VoIPphone or handset, which is able to wirelessly send and receive dataand/or signals to and from a network node, such as network node 700 aand/or other wireless devices 710. For example, wireless device 710 maytransmit wireless signals to one or more of network nodes 700 a-b,and/or receive wireless signals from one or more of network nodes 700a-b. The wireless signals may contain voice traffic, data traffic,control signals, and/or any other suitable information. In someembodiments, an area of wireless signal coverage associated with anetwork node 700 a may be referred to as a cell. In some embodiments,wireless device 710 may have device-to-device (D2D) capability. Thus,wireless device 710 may be able to receive signals from and/or transmitsignals directly to another wireless device.

Wireless device 710 comprises interface 711, processor 712, storage 713,antenna 714, and power source 715. Like network node 700, the componentsof wireless device 710 are depicted as single boxes located within asingle larger box, however in practice a wireless device may comprisesmultiple different physical components that make up a single illustratedcomponent (e.g., storage 713 may comprise multiple discrete microchips,each microchip representing a portion of the total storage capacity).

Interface 711 may be used in the wireless communication of signallingand/or data between wireless device 710 and network node 700. Forexample, interface 711 may perform any formatting, coding, ortranslating that may be needed to allow wireless device 710 to send andreceive data from network node 700 a over a wireless connection.Interface 711 may also include a radio transmitter and/or receiver thatmay be coupled to or a part of antenna 714. The radio may receivedigital data that is to be sent out to network node 700 a via a wirelessconnection. The radio may convert the digital data into a radio signalhaving the appropriate channel and bandwidth parameters. The radiosignal may then be transmitted via antenna 714 to network node 700.

Processor 712 may be a combination of one or more of a microprocessor,controller, microcontroller, central processing unit, digital signalprocessor, application specific integrated circuit, field programmablegate array, processing circuitry, or any other suitable computingdevice, resource, or combination of hardware, software and/or encodedlogic operable to provide, either alone or in combination with otherwireless device 710 components, such as storage 713, wireless device 710functionality. Such functionality may include providing various wirelessfeatures discussed herein, including any of the features or benefitsdisclosed herein.

Storage 713 may be any form of volatile or non-volatile memoryincluding, without limitation, persistent storage, solid state memory,remotely mounted memory, magnetic media, optical media, random accessmemory (RAM), read-only memory (ROM), removable media, or any othersuitable local or remote memory component. Storage 713 may store anysuitable data, instructions, or information, including software andencoded logic, utilized by wireless device 710. Storage 713 may be usedto store any calculations made by processor 712 and/or any data receivedvia interface 711.

Antenna 714 may be any type of antenna capable of transmitting andreceiving data and/or signals wirelessly. In some embodiments, antenna714 may comprise one or more omni-directional, sector or panel antennasoperable to transmit/receive radio signals between 2 GHz and 66 GHz. Forsimplicity, antenna 714 may be considered a part of interface 711 to theextent that a wireless signal is being used.

Power source 715 may comprise power management circuitry. Power source715 may receive power from a power supply, which may either be comprisedin, or be external to, power source 715. For example, wireless device710 may comprise a power supply in the form of a battery or batterypack, which is connected to, or integrated in, power source 715. Othertypes of power sources, such as photovoltaic devices, may also be used.As a further example, wireless device 710 may be connectable to anexternal power supply (such as an electricity outlet) via an inputcircuitry or interface such as an electrical cable, whereby the externalpower supply supplies power to power source 715. Power source 715 may beelectrically coupled to interface 711, processor 712, storage 713, andbe configured to supply wireless device 710 with power for performingthe functionality described herein.

In certain embodiments, network nodes 700 a may interface with a radionetwork controller. The radio network controller may control networknodes 700 a and may provide certain radio resource management functions,mobility management functions, and/or other suitable functions. Incertain embodiments, the functions of the radio network controller maybe performed by network node 700. The radio network controller mayinterface with a core network node. In certain embodiments, the radionetwork controller may interface with the core network node via aninterconnecting network. The interconnecting network may refer to anyinterconnecting system capable of transmitting audio, video, signals,data, messages, or any combination of the preceding. The interconnectingnetwork may include all or a portion of a PSTN, a public or private datanetwork, a local area network (LAN), a metropolitan area network (MAN),a wide area network (WAN), a local, regional, or global communication orcomputer network such as the Internet, a wireline or wireless network,an enterprise intranet, or any other suitable communication link,including combinations thereof. FIG. 8 describes additionalfunctionality of a radio network controller.

In some embodiments, the core network node may manage the establishmentof communication sessions and various other functionalities for wirelessdevice 710. Wireless device 710 may exchange certain signals with thecore network node using the non-access stratum (NAS) layer. Innon-access stratum signaling, signals between wireless devices 710 andthe core network node may be transparently passed through the radioaccess network. In certain embodiments, network nodes 700 a mayinterface with one or more network nodes over an internode interface.For example, network nodes 700 a and 700 b may interface over an X2interface.

Although FIG. 7 illustrates a particular arrangement of a wirelessnetwork, the present disclosure contemplates that the variousembodiments described herein may be applied to a variety of networkshaving any suitable configuration. For example, the wireless network mayinclude any suitable number of wireless devices 710 and network nodes700, as well as any additional elements suitable to supportcommunication between wireless devices or between a wireless device andanother communication device (such as a landline telephone).Furthermore, although certain embodiments may be described asimplemented in a long-term evolution (LTE) network, the embodiments maybe implemented in any appropriate type of telecommunication systemsupporting any suitable communication standards and using any suitablecomponents, and are applicable to any RAT or multi-RAT systems in whichthe wireless device receives and/or transmits signals (e.g., data). Forexample, the various embodiments described herein may be applicable toNR, LTE, LTE-Advanced, UMTS, HSPA, GSM, cdma2000, WiMax, WiFi, anothersuitable radio access technology, or any suitable

FIG. 8 is a schematic block diagram of an exemplary radio networkcontroller or core network node 810, in accordance with certainembodiments. In some embodiments a user equipment or wireless device mayhave a similar structure. Examples of network nodes can include a mobileswitching center (MSC), a serving GPRS support node (SGSN), a mobilitymanagement entity (MME), a radio network controller (RNC), a basestation controller (BSC), and so on. The radio network controller orcore network node 810 includes processor 820, memory 830, and networkinterface 840. In some embodiments, processor 820 executes instructionsto provide some or all of the functionality described above as beingprovided by the network node, memory 830 stores the instructionsexecuted by processor 820, and network interface 840 communicatessignals to any suitable node, such as a gateway, switch, router,Internet, Public Switched Telephone Network (PSTN), network nodes 100,radio network controllers or core network nodes 810, etc.

Processor 820 may include any suitable combination of hardware andsoftware implemented in one or more modules to execute instructions andmanipulate data to perform some or all of the described functions of theradio network controller or core network node 810. In some embodiments,processor 820 may include, for example, one or more computers, one ormore central processing units (CPUs), one or more microprocessors, oneor more applications, and/or other logic.

Memory 830 is generally operable to store instructions, such as acomputer program, software, an application including one or more oflogic, rules, algorithms, code, tables, etc. and/or other instructionscapable of being executed by a processor. Examples of memory 830 includecomputer memory (for example, Random Access Memory (RAM) or Read OnlyMemory (ROM)), mass storage media (for example, a hard disk), removablestorage media (for example, a Compact Disk (CD) or a Digital Video Disk(DVD)), and/or or any other volatile or non-volatile, non-transitorycomputer-readable and/or computer-executable memory devices that storeinformation.

In some embodiments, network interface 840 is communicatively coupled toprocessor 820 and may refer to any suitable device operable to receiveinput for the network node, send output from the network node, performsuitable processing of the input or output or both, communicate to otherdevices, or any combination of the preceding. Network interface 840 mayinclude appropriate hardware (e.g., port, modem, network interface card,etc.) and software, including protocol conversion and data processingcapabilities, to communicate through a network.

Other embodiments of the network node may include additional componentsbeyond those shown in FIG. 8 that may be responsible for providingcertain aspects of the network node's functionality, including any ofthe functionality described above and/or any additional functionality(including any functionality necessary to support the embodimentsdescribed above).

FIG. 9 is a schematic block diagram of an exemplary wireless device 902,in accordance with certain embodiments. Wireless device 902 may includeone or more modules. For example, wireless device 902 may include adetermining module 910, a communication module 920, and a receivingmodule 930. Optionally, wireless device 902 may include an input module940, a display module 950, and any other suitable modules. Wirelessdevice 902 may perform one or more of the embodiments described herein.

Determining module 910 may perform the processing functions of wirelessdevice 902. In one example embodiment, determining module 910 maydetermine that it has received one or more transmission parametersassociated with a successful beam recovery and implement the one or moretransmission parameters for re-configuration.

Determining module 910 may include or be included in one or moreprocessors, such as processor 112 described above in relation to FIG. 7.Determining module 910 may include analog and/or digital circuitryconfigured to perform any of the functions of determining module 910and/or processor 112 described above. The functions of determiningmodule 910 described above may, in certain embodiments, be performed inone or more distinct modules.

Communication module 920 may perform the communication functions ofwireless device 902. In certain embodiments, communication module 920may perform any of the communication functions described herein.Communication module 920 may include a transmitter and/or a transceiver,such as interface 111 and/or antenna 114 described above in relation toFIG. 7. Communication module 920 may include circuitry configured towirelessly transmit messages and/or signals. In particular embodiments,communication module 920 may receive messages and/or signals fortransmission from determining module 910. In certain embodiments, thefunctions of communication module 920 described above may be performedin one or more distinct modules.

Receiving module 930 may perform the receiving functions of wirelessdevice 902. In certain embodiments, receiving module 930 may perform anyof the receiving functions of a wireless device (e.g., wireless device710). In one example embodiment, receiving module 930 may receive one ormore transmission parameters from network node 100 in response to asuccessful beam recovery. Receiving module 930 may include a receiverand/or a transceiver, such as interface 111 and/or antenna 114 describedabove in relation to FIG. 7. Receiving module 930 may include circuitryconfigured to wirelessly receive messages and/or signals. In particularembodiments, receiving module 930 may communicate received messagesand/or signals to determining module 910.

Optionally, wireless device 902 may include input module 940. Inputmodule 940 may receive user input intended for wireless device 902. Forexample, the input module may receive key presses, button presses,touches, swipes, audio signals, video signals, and/or any otherappropriate signals. The input module may include one or more keys,buttons, levers, switches, touchscreens, microphones, and/or cameras.The input module may communicate received signals to determining module910.

Optionally, wireless device 902 may include display module 950. Displaymodule 950 may present signals on a display of wireless device 902.Display module 950 may include the display and/or any appropriatecircuitry and hardware configured to present signals on the display.Display module 950 may receive signals to present on the display fromdetermining module 910.

Determining module 910, communication module 920, receiving module 930,input module 940, and display module 950 may include any suitableconfiguration of hardware and/or software. Wireless device 902 mayinclude additional modules beyond those shown in FIG. 9 that may beresponsible for providing any suitable functionality, including any ofthe functionality described above and/or any additional functionality(including any functionality necessary to support the variousembodiments described herein).

FIG. 10 is a schematic block diagram of an exemplary network node 1000,in accordance with certain embodiments. Network node 1000 may includeone or more modules. For example, network node 1000 may includedetermining module 1010, communication module 1020, receiving module1030, and any other suitable modules. In some embodiments, one or moreof determining module 1010, communication module 1020, receiving module1030, or any other suitable module may be implemented using one or moreprocessors, such as processor 102 described above in relation to FIG. 7.In certain embodiments, the functions of two or more of the variousmodules may be combined into a single module. Network node 1000 mayperform one or more steps performed by network node(s) described herein.

Determining module 1010 may perform the processing functions of networknode 1000. In certain embodiments, determining module 1010 may performany of the functions of network node(s) described herein. In one exampleembodiment, determining module 1010 may determine that a successful beamrecovery has occurred and determine one or more transmission parametersassociated with the successful beam recovery.

Determining module 1010 may include or be included in one or moreprocessors, such as processor 102 described above in relation to FIG. 7.Determining module 1010 may include analog and/or digital circuitryconfigured to perform any of the functions of determining module 1010and/or processor 102 described above. The functions of determiningmodule 1010 may, in certain embodiments, be performed in one or moredistinct modules. For example, in certain embodiments some of thefunctionality of determining module 1010 may be performed by anallocation module.

Communication module 1020 may perform the transmission functions ofnetwork node 1000. In certain embodiments, network node 1000 may performany of the functions of the network node(s) described herein. In oneexample embodiment, communication module 1020 may transmit one or moretransmission parameters to configure/re-configure wireless device 110 inresponse to a successful beam recovery.

Communication module 1020 may transmit messages to one or more ofwireless devices 110. Communication module 1020 may include atransmitter and/or a transceiver, such as transceiver 1010 describedabove in relation to FIG. 7. Communication module 1020 may includecircuitry configured to wirelessly transmit messages and/or signals. Inparticular embodiments, communication module 1020 may receive messagesand/or signals for transmission from determining module 1010 or anyother module.

Receiving module 1030 may perform the receiving functions of networknode 1000. In certain embodiments, receiving module 1030 may perform anyof the functions of the network node(s) described herein. Receivingmodule 1030 may receive any suitable information from wireless device110 Receiving module 1030 may include a receiver and/or a transceiver,such as interface 101 and/or antenna 104, which are described above inrelation to FIG. 7. Receiving module 1030 may include circuitryconfigured to wirelessly receive messages and/or signals. In particularembodiments, receiving module 1030 may communicate received messagesand/or signals to determining module 1010 or any other suitable module.

Determining module 1010, communication module 1020, and receiving module1030 may include any suitable configuration of hardware and/or software.Network node 1000 may include additional modules beyond those shown inFIG. 10 that may be responsible for providing any suitablefunctionality, including any of the functionality described above and/orany additional functionality (including any functionality necessary tosupport the various embodiments described herein).

FIG. 11 illustrates an example of a signal flow between wireless device1110 and network node 1100. In some examples, wireless device 1110 andnetwork node 1100 are provided by a wireless device 710 and network node700 a as shown in FIG. 7, respectively. In some examples, network node1100 includes a combination of one or more nodes in the network, such asnetwork nodes 700 a and 700 b.

At step 1102, network node 1100 determines that a successful beamrecovery has occurred. In more detail regarding beam recovery, oncerecovery is performed subsequent failures can occur and be detected bythe wireless device 1110, which can transmit beam recovery requests andreceive a response from the network node 1100.

At step 1104, network node 1100 determines one or more transmissionparameters corresponding to the beam recovery. Upon beam recovery, thenetwork node 1100 can re-configure the transmission resources of beamrecovery requests, such as the time/frequency resources on which the UEmay transmit its request and/or the sequence and/or candidatesequence(s) (e.g., Physical Random Access Channel (PRACH) preambles). Asadditional examples, the network node 1100 can also modify the requestmethod from Physical Uplink Control Channel (PUCCH)-based to PRACH-basedor from PRACH-based to PUCCH-based depending on the resource situationof the different areas of the cell (which could even be different TRPsafter the selection).

In more detail, certain embodiments may include different beam recoveryresponse parameters. As an example of considerations that may be takeninto account in determining the parameters, the beam direction thewireless device 1110 selects may have changed. Accordingly, the networknode 1100 may change the RS type to be monitored (which could either bethe same as in RLM or different), one or multiple thresholds for thenumber of events that trigger beam failure detection (e.g. number ofout-of-sync events generated based on radio link quality based oncertain monitored beam), periodicities, monitored beam and/or beam linkpair(s). Moreover, when the network node 1100 indicates that thewireless device 1110 should remain monitoring CSI-RS resources for thatpurpose, the network can re-configure the resources to be monitored(based on the fact the direction has changed), the Rx beam(s) to be usedfor monitoring, and any other criteria to trigger sub-sequent beamfailure detection.

In another example, because beam recovery failures can occur, thenetwork node 1100 may determine to re-configure failure relatedparameters for the wireless device 1110 such as the maximum number ofattempts, power ramping parameters, beam switching parameters, receptionwindow, among others. In certain embodiments, different cell qualityderivation parameters can be used after beam recovery, such as themaximum number of beams to compute cell quality and the absolutethreshold for selecting beams other than the best for the average thatcomputes cell quality. For example, the wireless device 1110 may be inan area covered by a given cell (and having a certain distribution ofneighbor cells and/or beams from neighbor cells) so that the usage of anaverage with a certain maximum number of beams is suitable but afterrecovering and having another best beam (or best beam link pair(s)) thenetwork node 1100 may find it more suitable and/or optimized to use thebest beam only or reduce the number of beams. These could be amodification of an existing measurement object or even the addition orremoval of that (assuming that cell quality parameters are derived basedon that).

Certain embodiments may utilize one or more different beam reportingmechanisms e.g., RSRP, CSI reporting or CSI-like. The wireless device1110 may have an activated configuration to report CSI but, afterfailure, it recovers by selecting a beam (e.g. based on CSI-RS) fromanother TRP that has a different load and/or beamforming capabilities.Hence, the network node 1100 may determine to activate the reporting ofRSP (or equivalently less granular and lower overhead metric).

In some embodiments there are different RS Type per reportConfig for RRMmeasurements. The wireless device 1110 may activate CSI-RS basedmeasurements for cell measurement results with the purpose to triggerevent-based measurement reporting. However, after selecting another beamrecovery, and selection to another beam, the network node 1100 maydetermine to re-configure the wireless device 1110 to use another RStype (e.g., SS Block based RS, such as NR-SSS or DRMS of PBCH) that maybe useful if the wireless device 1110 selects a beam from a TRP close toan area where CSI-RS neighbor cell configurations are either unknown tothe wireless device 1110 or to a serving gNodeB.

Additional examples of parameters that may be determined and transmittedare described in more detail below with respect to step 1106. At step1106, network node 1100 transmits one or more transmission parameters toconfigure/re-configure wireless device 1110. In some examples, there-configuration upon beam recovery includes a transmission of a fulland/or delta re-configuration message, which can either be an RRCConnection Re-configuration or a MAC CE message containing the newparameters to be used and/or indicate previously configured andactivated parameters that can remain active. The wireless device 1110can expect an RRC Connection Re-configuration message (withoutmobilityControlInfo, for example, if recovery occurs within the samePCell) after a beam recovery containing a full and/or deltaconfiguration. There can also be a specific message defined for thepurpose of re-configuring the UE upon beam recovery, such as a new RRCmessage, or a MAC CE message, or any MAC like message.

The MAC CE may be as defined in LTE, where each bit in the CE activatesa single resource. Or, as shown in FIG. 2B, one bit inside the octet maypoint to a set of CSI-RSs. In some examples, there is a fixed definitionthat one bit points to all CSI-RSs configured with quasi-colocationmapping to a specific SSB. In other examples, the mapping includes aseparate set of lists of CSI-RS configurations where each bit in the MACCE points to one set which comprises a list of given CSI-RSconfigurations. Here, the MAC CE can also be used in normal operationand not only in HO. Accordingly, for the MAC CE one bit may point to apredefined/configuration (for example, a new list of CSI-RS resources).In some examples, there is a list per SSB beam or list per TRP.

Embodiments of the present disclosure include the possibility that thenetwork has initially assigned a configuration type of re-configurationsthat can be pre-loaded and later activated by the MAC CE basedmechanisms. For example, the network node 1100 may know that upon beamrecovery, regardless which best beam the wireless device 1110 selectsafter detecting the failure, only the CSI-RS resources being monitoredwould change. Accordingly, the network node 1100 can indicate the changein the monitored CSI-RS resources via the RRC messages previouslydescribed (i.e. as a recovery configuration). In that case, the numberof indexes to be used and indicated in the MAC CE after recovery can bereduced. For example, there can be a configuration type associated toCSI-RS configurations for beam management where the wireless device 1110should monitor beams and report them. Each configuration can be a subsetof CSI-RS resources (e.g., time/frequency/sequence) associated with DLbeams of a given cell, where upon beam recovery based on the selectionof a new beam (e.g. based on a wide beam SS Block), the wireless device1110 would be re-configured with a new set of CSI-RS resourcestransmitted now in a correlated manner with the new SS Block.

At step 1108, wireless device 1110 receives the one or more transmissionparameters and implements the one or more transmission parameters tocomplete the re-configuration. In some examples, the wireless device1110 receives a list of candidate re-configurations that are indexed(e.g., by an integer value) and one or a subset of these can be furtheractivated by the re-configuration upon beam recovery. In some examples,the wireless device 1110 receives the index to a previously receivedconfiguration, which can then be activated by the wireless device 1110due to the change of a beam after beam recovery. The wireless device1110 can receive the list of candidate configurations via an RRCConnection Resume and/or an RRC Connection Re-configuration (withmobilityControlInfo in the case a target cell is providing the UE thatlist to be later used after HO execution) and/or RRC ConnectionRe-configuration (without mobilityControlInfo in the case or intra-cellprocedure) and/or an RRC Connection Setup (e.g., when the UE is tryingto connect to a cell). Each configuration in the list can be indexed,and, upon sending a beam failure detection request the wireless device1110 expects a response message that may contain an indication of thenew index to be activated, such that the wireless device 1110 candeactivate a previously active configuration.

In some examples, when the wireless device 1110 has been previouslyconfigured with a set of candidate configurations and an index perconfiguration, a configuration can be activated by an indicationtransmitted in a MAC based message, such as a random access responseand/or a MAC CE. That can be the first MAC message the wireless device1110 expects after transmitting the beam recovery request or asubsequent message after the wireless device 1110 receives a MAC basedmessage confirming the reception of the request.

Modifications, additions, or omissions may be made to the systems andmethods described herein without departing from the scope of thedisclosure. The methods may include more, fewer, or other steps.Additionally, steps may be performed in any suitable order. Any of theembodiments described in this document may be combined in any way witheach other. Although this disclosure has been described in terms ofcertain embodiments, alterations and permutations of the embodimentswill be apparent to those skilled in the art. Accordingly, the abovedescription of the embodiments does not constrain this disclosure. Otherchanges, substitutions, and alterations are possible without departingfrom the spirit and scope of this disclosure, as defined by thefollowing claims.

1. A method at a network node (1100) for connection re-configurationupon beam recovery, the method comprising: determining (1102) that asuccessful beam recovery has occurred corresponding to a wireless device(1110); determining (1104) one or more transmission parametersassociated with the successful beam recovery, the one or moretransmission parameters for re-configuring (1108) the wireless device(1110); and transmitting (1108) the one or more transmission parametersto the wireless device (1110).
 2. The method of claim 1, wherein a RadioResource Control, RRC, connection re-configuration message is used totransmit the one or more transmission parameters.
 3. The method of claim1, wherein a Medium Access Control, MAC, Coverage Enhancement, CE,message is used to transmit the one or more transmission parameters,wherein each bit in the MAC CE indicates a configuration of one or moreChannel State Information Reference Signal, CSI-RS, resources.
 4. Themethod of any of claims 1-3, wherein the one or more transmissionparameters include at least one of: an RS type to be monitored; one ormultiple thresholds for a number of events that trigger a beam failuredetection; one or more periodicities; one or more monitored beam or beamlink pair(s); or one or more Rx beam(s) to be used for monitoring. 5.The method of any of claims 1-4, wherein the one or more transmissionparameters include at least one of: a time and/or frequency resourcethat the wireless device transmits a subsequent beam recovery requests;a sequence that the wireless device transmits the subsequent beamrecovery request; or a request method that the wireless device that thewireless device uses to transmit the subsequent beam recovery request,wherein the transmission parameters re-configure the request method from(1) a Physical Uplink Control Channel, PUCCH, request method to aPhysical Random Access Channel, PRACH, request method or (2) from thePRACH request method to the PUCCH request method.
 6. The method of anyof claims 1-5, wherein the one or more transmission parameters includeat least one of a reception window parameter, a maximum number offailure recovery attempts parameter, a power ramping parameter, or abeam switching parameter.
 7. The method of any of claims 1-6, whereinthe one or more transmission parameters specify (i) a maximum number ofbeams to compute cell quality and (ii) an absolute threshold forselecting beams for computing an average that indicates cell quality. 8.The method of any of claims 1-7, wherein each of the one or moretransmission parameters indicate a change to a previously configuredparameter, and wherein one or more other previously configuredparameters remain unchanged.
 9. The method of any of claims 1-8, furthercomprising: transmitting, to the wireless device, an index of candidatere-configurations, wherein the transmitted one or more transmissionparameters activate one or more of the indexed candidatere-configurations.
 10. A method at a wireless device (1110) forconnection re-configuration upon beam recovery, the method comprising:receiving (1106) one or more transmission parameters from a network node(1100), wherein the one or more transmission parameters are associatedwith a successful beam recovery; and implementing (1108) the one or moretransmission parameters received from the network node (1100).
 11. Themethod of claim 10, wherein the transmission parameters are received aspart of a Radio Resource Control, RRC, connection re-configurationmessage from the network node.
 12. The method of claim 10, wherein theone or more transmission parameters are received as part of a MediumAccess Control, MAC, Coverage Enhancement, CE, message from the networknode, wherein each bit in the MAC CE indicates a configuration of one ormore Channel State Information Reference Signal, CSI-RS, resources. 13.The method of any of claims 10-12, further comprising: receiving aplurality of candidate re-configurations; and determining one or more ofthe plurality of candidate re-configurations for activation upon beamrecovery.
 14. The method of claim 13, wherein the plurality of candidatere-configurations is received via at least one of: an RRC Connectionresume message; an RRC connection re-configuration message withmobilityControlInfo; an RRC connection re-configuration message withoutmobilityControlInfo; or an RRC connection setup message.
 15. The methodof any of claims 13-14, wherein the plurality of candidatere-configurations are indexed.
 16. The method of any of claims 13-15,further comprising: receiving an indication from the network node, theindication activating one of the plurality of candidatere-configurations.
 17. The method of claim 16, wherein the indication isreceived as part of a MAC based message, wherein the MAC based messageincludes at least one of: a random access response message; or a MAC CE.18. A network node (1100) comprising: processing circuitry (702)configured to: determine (1102) that a successful beam recovery hasoccurred; determine (1104) one or more transmission parametersassociated with the successful beam recovery, the one or moretransmission parameters for re-configuring a wireless device (1110); andan interface (701) operably coupled to the processing circuitry (702),the interface configured to: transmit (1106) the one or moretransmission parameters to the wireless device (1110).
 19. The networknode of claim 18, further configured to perform any of the methods ofclaims 2-9.
 20. A wireless device (1110) comprising: an interface (711)configured to receive (1106) one or more transmission parameters from anetwork node (1100), wherein the one or more transmission parameters areassociated with a successful beam recovery; and processing circuitry(712) operably coupled to the interface, the processing circuitry (712)configured to implement (1108) the one or more transmission parametersreceived from the network node.
 21. The wireless device of claim 20,further configured to perform any of the methods of claims 11-17.
 22. Acomputer program product (810) comprising a non-transitory computerreadable medium (840) storing computer readable program code, thecomputer readable program code operable, when executed by processingcircuitry (820) to perform any of the methods of claims 1-9.
 23. Acomputer program product (810) comprising a non-transitory computerreadable medium (840) storing computer readable program code, thecomputer readable program code operable, when executed by processingcircuitry (820) to perform any of the methods of claims 10-17.
 24. Asystem for connection re-configuration upon beam recovery comprising: anetwork node (1100) configured to perform operations comprising:determining (1102) that a successful beam recovery has occurred with awireless device (1110); determining (1104) one or more transmissionparameters associated with the successful beam recovery, the one or moretransmission parameters for re-configuring the wireless device (1110);and transmitting (1106) the one or more transmission parameters to thewireless device; and the wireless device (1110) configured to performoperations comprising: receiving (1106) the one or more transmissionparameters from the network node; and implementing (1108) the one ormore transmission parameters received from the network node (1100). 25.The system of claim 24, wherein the network node is further configuredto perform the methods of any of claims 2-9.
 26. The system of claim 24,wherein the wireless device is further configured to perform the methodsof any of claims 11-17.